Thanks @ity ! This code is... hard to test, unfortunately. We need to get an end-to-end remoting test working, possibly via #7553, but until then: fine as is.

If we're going to rely on spinning up scoot or something for integration testing here, we should think about doing so in a docker container, to avoid absolute paths happening to be present on the machine :)

Thanks @ity ! This code is... hard to test, unfortunately. We need to get an end-to-end remoting test working, possibly via #7553, but until then: fine as is.

If we're going to rely on spinning up scoot or something for integration testing here, we should think about doing so in a docker container, to avoid absolute paths happening to be present on the machine :)

thats sounds great to me!

Thanks @ity ! This code is... hard to test, unfortunately. We need to get an end-to-end remoting test working, possibly via #7553, but until then: fine as is.

If we're going to rely on spinning up scoot or something for integration testing here, we should think about doing so in a docker container, to avoid absolute paths happening to be present on the machine :)

Mm, good point. Or maybe explicitly using RBE from an integration test will be reasonable sometime soon. cc @Eric-Arellano

I don’t think remoting an integration test will happen soon, unfortunately, due to starting teaching soon. Unless we expect it to be trivial to remote integration tests after we remote unit tests, which I don’t anticipate.

Unit tests should be soon! It seems all we need is to finish this token generator.